Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75ec5a4b060d4cec13e770ba4645e6652f4d13306e47baba4383686fc3c9353f

Tx prefix hash: e7d103cc8651f765758ece8f3d00b8f10981fa093062681e65126339f876d70c
Tx public key: f540b0e9a37466a8d64a98dd97cc6ea7c463cc53cc1ae1a251741ecf821e7489
Timestamp: 1693395408 Timestamp [UCT]: 2023-08-30 11:36:48 Age [y:d:h:m:s]: 01:223:08:45:15
Block: 837166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 420758 RingCT/type: yes/0
Extra: 01f540b0e9a37466a8d64a98dd97cc6ea7c463cc53cc1ae1a251741ecf821e748902110000000733af99f4000000000000000000

1 output(s) for total of 1.033050598000 dcy

stealth address amount amount idx
00: 107c3cc90fd0805ab0b7ed3ef5540e1f90f25384bd88527219f6f7ceb447b5a3 1.033050598000 1289778 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": 837176, "vin": [ { "gen": { "height": 837166 } } ], "vout": [ { "amount": 1033050598, "target": { "key": "107c3cc90fd0805ab0b7ed3ef5540e1f90f25384bd88527219f6f7ceb447b5a3" } } ], "extra": [ 1, 245, 64, 176, 233, 163, 116, 102, 168, 214, 74, 152, 221, 151, 204, 110, 167, 196, 99, 204, 83, 204, 26, 225, 162, 81, 116, 30, 207, 130, 30, 116, 137, 2, 17, 0, 0, 0, 7, 51, 175, 153, 244, 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