Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f090b04260f5df06bc8a2aa4ea5fcb81a6b8e9a446d50581e37eaca142dcad0

Tx prefix hash: 5e90e45fdf44f755ccd9046c187773ed2377b84b777daa2f7351c0de80eaddf1
Tx public key: 051628f64cf459a2a2b009f98d93ef4df97ab22b2e74a8243456e628a5bfe977
Timestamp: 1718407868 Timestamp [UCT]: 2024-06-14 23:31:08 Age [y:d:h:m:s]: 01:147:01:25:48
Block: 1044358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363658 RingCT/type: yes/0
Extra: 01051628f64cf459a2a2b009f98d93ef4df97ab22b2e74a8243456e628a5bfe9770211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aba01194fce98b18cd4504d8f9e0a86758f23b4d194db14e489a8c4af9828b5a 0.600000000000 1513647 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": 1044368, "vin": [ { "gen": { "height": 1044358 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aba01194fce98b18cd4504d8f9e0a86758f23b4d194db14e489a8c4af9828b5a" } } ], "extra": [ 1, 5, 22, 40, 246, 76, 244, 89, 162, 162, 176, 9, 249, 141, 147, 239, 77, 249, 122, 178, 43, 46, 116, 168, 36, 52, 86, 230, 40, 165, 191, 233, 119, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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