Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfec109ed4a765a6c328d52bca759eb9916d453b6e35a029bfb30973f56c02ff

Tx prefix hash: cc2b0c5a28431359c4b55d9b5984d378c77069d8f3994937e67022a8088780cf
Tx public key: e600b058f1640486b5d8ea20ca5c2c281697d575efd254a4b00403ae795d8bb9
Timestamp: 1745861707 Timestamp [UCT]: 2025-04-28 17:35:07 Age [y:d:h:m:s]: 00:205:14:26:22
Block: 1271449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 144656 RingCT/type: yes/0
Extra: 01e600b058f1640486b5d8ea20ca5c2c281697d575efd254a4b00403ae795d8bb902110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1bec5893e9905d4bcc8585f52937d51623f73d5d317a65f28ad442154de9c51 0.600000000000 1758710 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": 1271459, "vin": [ { "gen": { "height": 1271449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1bec5893e9905d4bcc8585f52937d51623f73d5d317a65f28ad442154de9c51" } } ], "extra": [ 1, 230, 0, 176, 88, 241, 100, 4, 134, 181, 216, 234, 32, 202, 92, 44, 40, 22, 151, 213, 117, 239, 210, 84, 164, 176, 4, 3, 174, 121, 93, 139, 185, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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