Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e065bccd1469e79c81e648a6c25099e7e408ad4f1b2f44f9b9e807d0c4bad75

Tx prefix hash: 469e937da20512e66576e667c9da5568e1a17424ff052f3389469de2257f39b8
Tx public key: bae819801bc609056374ee9cae82513a8e0504b5d7cc0ff9afcb052c6662be5b
Timestamp: 1740848457 Timestamp [UCT]: 2025-03-01 17:00:57 Age [y:d:h:m:s]: 00:263:11:48:13
Block: 1229935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186077 RingCT/type: yes/0
Extra: 01bae819801bc609056374ee9cae82513a8e0504b5d7cc0ff9afcb052c6662be5b021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f11f3ff328e33bbfaaa81bc86dd5247b692e3e464f97ac5b4e5f8942622c88a9 0.600000000000 1716826 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": 1229945, "vin": [ { "gen": { "height": 1229935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f11f3ff328e33bbfaaa81bc86dd5247b692e3e464f97ac5b4e5f8942622c88a9" } } ], "extra": [ 1, 186, 232, 25, 128, 27, 198, 9, 5, 99, 116, 238, 156, 174, 130, 81, 58, 142, 5, 4, 181, 215, 204, 15, 249, 175, 203, 5, 44, 102, 98, 190, 91, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 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