Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 314182f846d99c507e4070b5139527b29d07a0fafac461d8adc31aae0bc5b05f

Tx prefix hash: 6f9b4a1328cf2e4689e600d2f3df42feaf53c26d5a3ed93eabce06e1092724a0
Tx public key: ad7fff3915eaf5da3a0ecb85921f3aa6a701aa1d50569638c5d69ce5aa6a7438
Timestamp: 1718023546 Timestamp [UCT]: 2024-06-10 12:45:46 Age [y:d:h:m:s]: 00:279:22:51:51
Block: 1041173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200076 RingCT/type: yes/0
Extra: 01ad7fff3915eaf5da3a0ecb85921f3aa6a701aa1d50569638c5d69ce5aa6a743802110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d61b96a99eeb1507d649d3dce02ed92296073808860fbe52e499bf6ef67a0064 0.600000000000 1509838 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": 1041183, "vin": [ { "gen": { "height": 1041173 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d61b96a99eeb1507d649d3dce02ed92296073808860fbe52e499bf6ef67a0064" } } ], "extra": [ 1, 173, 127, 255, 57, 21, 234, 245, 218, 58, 14, 203, 133, 146, 31, 58, 166, 167, 1, 170, 29, 80, 86, 150, 56, 197, 214, 156, 229, 170, 106, 116, 56, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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