Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5ee0f968470b0d6429fb1f434d1358581fe448d5829b2dcde5341263c117a3c

Tx prefix hash: 70d75bc84dfc54702d58dee6ea152c49abaca3ced65bf3f12d53c6eb98315585
Tx public key: 33ced63ba015ea4a178a0fb4d7aa7c7def155caa26ff4191738f7a414ecfecbd
Timestamp: 1713233875 Timestamp [UCT]: 2024-04-16 02:17:55 Age [y:d:h:m:s]: 00:318:13:13:38
Block: 1001449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227723 RingCT/type: yes/0
Extra: 0133ced63ba015ea4a178a0fb4d7aa7c7def155caa26ff4191738f7a414ecfecbd02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46c82e5276e57f3d173b6ca13a3a44a8f2f8f424f51fd8feedd27bea2e61875e 0.600000000000 1461953 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": 1001459, "vin": [ { "gen": { "height": 1001449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46c82e5276e57f3d173b6ca13a3a44a8f2f8f424f51fd8feedd27bea2e61875e" } } ], "extra": [ 1, 51, 206, 214, 59, 160, 21, 234, 74, 23, 138, 15, 180, 215, 170, 124, 125, 239, 21, 92, 170, 38, 255, 65, 145, 115, 143, 122, 65, 78, 207, 236, 189, 2, 17, 0, 0, 0, 6, 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