Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5dac293ac5ca2a1d99c3143a2135ae024d03d4f1b9f00aacb7ec135ceed648a3

Tx prefix hash: 12eba30d1371947b9c8818808c6b02d0b73cf3aec155bd7a902c7bcb7e99594b
Tx public key: 0765a3693c89593502507a40f16d7c3a93b77c1178faa095c38c2bd1ee712ab4
Timestamp: 1715629052 Timestamp [UCT]: 2024-05-13 19:37:32 Age [y:d:h:m:s]: 00:325:10:48:49
Block: 1021320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232623 RingCT/type: yes/0
Extra: 010765a3693c89593502507a40f16d7c3a93b77c1178faa095c38c2bd1ee712ab40211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea3a41f09b962d9ee61bd4769e4311a2aec7dcee0514ce17ee8fcc25881614dc 0.600000000000 1485607 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": 1021330, "vin": [ { "gen": { "height": 1021320 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea3a41f09b962d9ee61bd4769e4311a2aec7dcee0514ce17ee8fcc25881614dc" } } ], "extra": [ 1, 7, 101, 163, 105, 60, 137, 89, 53, 2, 80, 122, 64, 241, 109, 124, 58, 147, 183, 124, 17, 120, 250, 160, 149, 195, 140, 43, 209, 238, 113, 42, 180, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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