Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1bca59cec223d5f061c2d57fa78f3e6639fbd0b81439ddc4f2e21635c922fb5

Tx prefix hash: 45b7d36b65aee252b97716711e3c2546d204f41c6c6780181c764af17208e51f
Tx public key: 5b9cc7a2ed55f0217b9ced7da6afe9912518f01b76dd699fb3d10963d1a968fc
Timestamp: 1729185634 Timestamp [UCT]: 2024-10-17 17:20:34 Age [y:d:h:m:s]: 00:208:05:15:44
Block: 1133715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148608 RingCT/type: yes/0
Extra: 015b9cc7a2ed55f0217b9ced7da6afe9912518f01b76dd699fb3d10963d1a968fc0211000000033cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec56a368f319f2310a3eac5b2fded9d1d72825672339225ac6cb3cc997a92750 0.600000000000 1616902 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": 1133725, "vin": [ { "gen": { "height": 1133715 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec56a368f319f2310a3eac5b2fded9d1d72825672339225ac6cb3cc997a92750" } } ], "extra": [ 1, 91, 156, 199, 162, 237, 85, 240, 33, 123, 156, 237, 125, 166, 175, 233, 145, 37, 24, 240, 27, 118, 221, 105, 159, 179, 209, 9, 99, 209, 169, 104, 252, 2, 17, 0, 0, 0, 3, 60, 208, 252, 6, 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