Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: c50aa73906f46c54e41f70373af73513e48f0d25008600b9fe14b08fa249c736

Tx prefix hash: f330442fc2fbdd82a46659598a0a3752e2463f73b64d66741ebbd102ee9f6580
Tx public key: 41f5f250dfd02dce6a5e3f6d62ac4c18fd49d794416f1f27aa730ac06c189689
Timestamp: 1699099434 Timestamp [UCT]: 2023-11-04 12:03:54 Age [y:d:h:m:s]: 01:155:16:07:03
Block: 884498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372228 RingCT/type: yes/0
Extra: 0141f5f250dfd02dce6a5e3f6d62ac4c18fd49d794416f1f27aa730ac06c189689021100000008e6d27f9c000000000000000000

1 output(s) for total of 0.719931141000 dcy

stealth address amount amount idx
00: a0966dd91bc3339c9949c71e339c0aee01af0393ac44d18f9b1fcb59114e3787 0.719931141000 1340241 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 884508, "vin": [ { "gen": { "height": 884498 } } ], "vout": [ { "amount": 719931141, "target": { "key": "a0966dd91bc3339c9949c71e339c0aee01af0393ac44d18f9b1fcb59114e3787" } } ], "extra": [ 1, 65, 245, 242, 80, 223, 208, 45, 206, 106, 94, 63, 109, 98, 172, 76, 24, 253, 73, 215, 148, 65, 111, 31, 39, 170, 115, 10, 192, 108, 24, 150, 137, 2, 17, 0, 0, 0, 8, 230, 210, 127, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8