Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f3af69b22d55565d389d804496a75366a2f6bae65a06354f19373883c3aa7e8

Tx prefix hash: ef770486304b0eb7958c5661ff07b5a612abfcb88dbe556377f9bf26b4623001
Tx public key: 71deff38aff2c8c3c094b3762c0ab561108d8b97a21cc59fb883a0dc8521ee8e
Timestamp: 1748939245 Timestamp [UCT]: 2025-06-03 08:27:25 Age [y:d:h:m:s]: 00:163:23:17:40
Block: 1296939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114870 RingCT/type: yes/0
Extra: 0171deff38aff2c8c3c094b3762c0ab561108d8b97a21cc59fb883a0dc8521ee8e021100000002bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4caa7bbec7233bfaf0d7a6942866cf6dc61658a0a4d4cd3c3737665c9e2d6cc 0.600000000000 1784456 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": 1296949, "vin": [ { "gen": { "height": 1296939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4caa7bbec7233bfaf0d7a6942866cf6dc61658a0a4d4cd3c3737665c9e2d6cc" } } ], "extra": [ 1, 113, 222, 255, 56, 175, 242, 200, 195, 192, 148, 179, 118, 44, 10, 181, 97, 16, 141, 139, 151, 162, 28, 197, 159, 184, 131, 160, 220, 133, 33, 238, 142, 2, 17, 0, 0, 0, 2, 191, 81, 178, 162, 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