Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04d0fa3d63135b441590e5290f170e8b4b863e9107243e967c95a61e18830e2c

Tx prefix hash: 1de1177073004c14bdd43b41cef44509a2098800c50173b3e7300685b727b616
Tx public key: 0ac3737fbe58192cbd437e7f3effe90126769659c7cccfe5f7c420075a3dc0a3
Timestamp: 1627396315 Timestamp [UCT]: 2021-07-27 14:31:55 Age [y:d:h:m:s]: 03:115:22:05:57
Block: 302003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 855111 RingCT/type: yes/0
Extra: 010ac3737fbe58192cbd437e7f3effe90126769659c7cccfe5f7c420075a3dc0a30211000000196b458187000000000000000000

1 output(s) for total of 61.282882017000 dcy

stealth address amount amount idx
00: 2d722e115e903f39e425a687ca9c8e5d3aab0bdc4a1f7107a2ac5257edb76059 61.282882017000 630660 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": 302013, "vin": [ { "gen": { "height": 302003 } } ], "vout": [ { "amount": 61282882017, "target": { "key": "2d722e115e903f39e425a687ca9c8e5d3aab0bdc4a1f7107a2ac5257edb76059" } } ], "extra": [ 1, 10, 195, 115, 127, 190, 88, 25, 44, 189, 67, 126, 127, 62, 255, 233, 1, 38, 118, 150, 89, 199, 204, 207, 229, 247, 196, 32, 7, 90, 61, 192, 163, 2, 17, 0, 0, 0, 25, 107, 69, 129, 135, 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