Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55f101ec858baaead12959a3e2acc1b4628a33adccf26c63103259770fbebad0

Tx prefix hash: 15b729a35d235181b76b1a2ac475f004355888844c596854a70263f2f3190619
Tx public key: 8cb0cb4c025d38adacd89a7efdc8fc9bcfa30295b3b21df2c7c1b8162acd14ee
Timestamp: 1717516664 Timestamp [UCT]: 2024-06-04 15:57:44 Age [y:d:h:m:s]: 00:359:07:47:43
Block: 1036973 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256842 RingCT/type: yes/0
Extra: 018cb0cb4c025d38adacd89a7efdc8fc9bcfa30295b3b21df2c7c1b8162acd14ee02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 538c8ebe04fa264f5722ce907e8caa96181499502e389876c8370f730aa6d71b 0.600000000000 1505504 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": 1036983, "vin": [ { "gen": { "height": 1036973 } } ], "vout": [ { "amount": 600000000, "target": { "key": "538c8ebe04fa264f5722ce907e8caa96181499502e389876c8370f730aa6d71b" } } ], "extra": [ 1, 140, 176, 203, 76, 2, 93, 56, 173, 172, 216, 154, 126, 253, 200, 252, 155, 207, 163, 2, 149, 179, 178, 29, 242, 199, 193, 184, 22, 42, 205, 20, 238, 2, 17, 0, 0, 0, 1, 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