Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 340f67bc8cc5ed612858b29a60f891389192eb0b60714bab75f7dfaedcd733c0

Tx prefix hash: f5d0cc8af9c4d3eb358dbddd9cb51b336e6eb82c7fa7f06f45e66b39619131fa
Tx public key: 9daea768cf7bc40a2da29a6ca2594e160540f15f04b6766d9abaeea2fbfb69e3
Timestamp: 1721145680 Timestamp [UCT]: 2024-07-16 16:01:20 Age [y:d:h:m:s]: 00:258:21:15:47
Block: 1067065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184925 RingCT/type: yes/0
Extra: 019daea768cf7bc40a2da29a6ca2594e160540f15f04b6766d9abaeea2fbfb69e3021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ad1c13736deee3e819760a31cea6474483188dc271d0cf0f768a4e04aacb93d 0.600000000000 1537780 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": 1067075, "vin": [ { "gen": { "height": 1067065 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ad1c13736deee3e819760a31cea6474483188dc271d0cf0f768a4e04aacb93d" } } ], "extra": [ 1, 157, 174, 167, 104, 207, 123, 196, 10, 45, 162, 154, 108, 162, 89, 78, 22, 5, 64, 241, 95, 4, 182, 118, 109, 154, 186, 238, 162, 251, 251, 105, 227, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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