Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a37dec6cacff6a386a38f74897a582c61d1d9b689f5b365222901ea2e12b46ef

Tx prefix hash: fde35856852469e7147f7c8202b834686de7a16657e5feed525547914c1a1fe4
Tx public key: 7e158e7c869f8b1d50bcd8698eb3fbfb887e96c123d6a857784b8b05ac6c35d3
Timestamp: 1717084665 Timestamp [UCT]: 2024-05-30 15:57:45 Age [y:d:h:m:s]: 00:290:20:16:24
Block: 1033388 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207876 RingCT/type: yes/0
Extra: 017e158e7c869f8b1d50bcd8698eb3fbfb887e96c123d6a857784b8b05ac6c35d30211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ddf7c6f0f01f361e5bfb14cdbd9541d70ceb0e8e29a128c7762e55042804318f 0.600000000000 1501853 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": 1033398, "vin": [ { "gen": { "height": 1033388 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ddf7c6f0f01f361e5bfb14cdbd9541d70ceb0e8e29a128c7762e55042804318f" } } ], "extra": [ 1, 126, 21, 142, 124, 134, 159, 139, 29, 80, 188, 216, 105, 142, 179, 251, 251, 136, 126, 150, 193, 35, 214, 168, 87, 120, 75, 139, 5, 172, 108, 53, 211, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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