Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 931cdfa6a818eb02f6a59ee32f47148f30ed95e068ad384038ef9f11f4d7f355

Tx prefix hash: 9487e499e47f320679abeb05306d509933c5023740ca43bc49b1bef5a1b613cf
Tx public key: 55eeb1e856b94d04209f99a3a9e506635ce876a31210ee0588c02a2f88bee4d5
Timestamp: 1709751934 Timestamp [UCT]: 2024-03-06 19:05:34 Age [y:d:h:m:s]: 01:259:02:43:05
Block: 972600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443912 RingCT/type: yes/0
Extra: 0155eeb1e856b94d04209f99a3a9e506635ce876a31210ee0588c02a2f88bee4d502110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16d6cbed459fba9c95444040c7078ccc701655cd9de1b015ff5a15ac384acfa8 0.600000000000 1432517 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": 972610, "vin": [ { "gen": { "height": 972600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16d6cbed459fba9c95444040c7078ccc701655cd9de1b015ff5a15ac384acfa8" } } ], "extra": [ 1, 85, 238, 177, 232, 86, 185, 77, 4, 32, 159, 153, 163, 169, 229, 6, 99, 92, 232, 118, 163, 18, 16, 238, 5, 136, 192, 42, 47, 136, 190, 228, 213, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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