Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fafe709ac4946457f052d02e11cf59d8305c835f278748ff8bb7cd711027fed

Tx prefix hash: 485e1926d09d2d9fb61442974c35760d44e07d021c2747a688f1604f7be31566
Tx public key: 2bd5ab245c64017a7cc7b7fa0faf0d46660b1461030fb0e55982b433b75cb0e6
Timestamp: 1578852963 Timestamp [UCT]: 2020-01-12 18:16:03 Age [y:d:h:m:s]: 04:298:16:43:51
Block: 44138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1102904 RingCT/type: yes/0
Extra: 012bd5ab245c64017a7cc7b7fa0faf0d46660b1461030fb0e55982b433b75cb0e60211000000034ac5aa02000000000000000000

1 output(s) for total of 438.281687386000 dcy

stealth address amount amount idx
00: b3e667840b2df4b8b26780aa5472b74e3ab7fc4d3302536bf144a8402ab0869b 438.281687386000 80208 of 0

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": 44148, "vin": [ { "gen": { "height": 44138 } } ], "vout": [ { "amount": 438281687386, "target": { "key": "b3e667840b2df4b8b26780aa5472b74e3ab7fc4d3302536bf144a8402ab0869b" } } ], "extra": [ 1, 43, 213, 171, 36, 92, 100, 1, 122, 124, 199, 183, 250, 15, 175, 13, 70, 102, 11, 20, 97, 3, 15, 176, 229, 89, 130, 180, 51, 183, 92, 176, 230, 2, 17, 0, 0, 0, 3, 74, 197, 170, 2, 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