Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4125109e98d1b09c0215f23b0c563baa74990cbb5bf591e7c258d3ef1bba3f01

Tx prefix hash: 7ca0132daea4fe6c97149fb98051dd93fce79c320ea9779d8b38fcb70664d0c3
Tx public key: e927a3df0e18fc32f906a7b165bbe969fe15bcaf063feb19df66e33a0c386108
Timestamp: 1726641678 Timestamp [UCT]: 2024-09-18 06:41:18 Age [y:d:h:m:s]: 01:050:00:54:16
Block: 1112614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294172 RingCT/type: yes/0
Extra: 01e927a3df0e18fc32f906a7b165bbe969fe15bcaf063feb19df66e33a0c38610802110000001591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ee1ef4307dd75252a52b96eeb489ba69bb0f7314900b654e10f30a6d8e2da01 0.600000000000 1591997 of 15

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": 1112624, "vin": [ { "gen": { "height": 1112614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ee1ef4307dd75252a52b96eeb489ba69bb0f7314900b654e10f30a6d8e2da01" } } ], "extra": [ 1, 233, 39, 163, 223, 14, 24, 252, 50, 249, 6, 167, 177, 101, 187, 233, 105, 254, 21, 188, 175, 6, 63, 235, 25, 223, 102, 227, 58, 12, 56, 97, 8, 2, 17, 0, 0, 0, 21, 145, 225, 60, 4, 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