Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5fea90b40e6c4545bcc82258895a7a97eb6eb9698d757a0fc16f304caf97e25

Tx prefix hash: 1abcd4fa1b3a82fba056ee13a5d0e501ab44794df2dde3f6285d71f3ad0722de
Tx public key: af3364b8dd0792dfd9b660cf0ff8e1349978bcae62e56e1cbe4e56d57eb67cfc
Timestamp: 1749244728 Timestamp [UCT]: 2025-06-06 21:18:48 Age [y:d:h:m:s]: 00:166:10:42:41
Block: 1299455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116653 RingCT/type: yes/0
Extra: 01af3364b8dd0792dfd9b660cf0ff8e1349978bcae62e56e1cbe4e56d57eb67cfc02110000000443846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7a796ff130cc3c95a39c2fa97201da974748be325f9f3f244c1b9c57156f87b 0.600000000000 1786992 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": 1299465, "vin": [ { "gen": { "height": 1299455 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7a796ff130cc3c95a39c2fa97201da974748be325f9f3f244c1b9c57156f87b" } } ], "extra": [ 1, 175, 51, 100, 184, 221, 7, 146, 223, 217, 182, 96, 207, 15, 248, 225, 52, 153, 120, 188, 174, 98, 229, 110, 28, 190, 78, 86, 213, 126, 182, 124, 252, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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