Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa74e1401df0a90885dc2975e0e6bbb714ca2070879a096128b8201cd4274fd3

Tx prefix hash: 3e46b7ae07e22a7dca4d066b31601fbf798643bc620638c2cd3945afa71d546b
Tx public key: c67a0a9732782d2aee610dcebe2a78352aa6b5bdcc433fa3b0badd18fbda97c8
Timestamp: 1721273823 Timestamp [UCT]: 2024-07-18 03:37:03 Age [y:d:h:m:s]: 00:129:07:25:26
Block: 1068129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92512 RingCT/type: yes/0
Extra: 01c67a0a9732782d2aee610dcebe2a78352aa6b5bdcc433fa3b0badd18fbda97c802110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: deb2c98c064b91d9b34c806ef9c577853651305f3cae55da6b0b65bce9ad7255 0.600000000000 1539156 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": 1068139, "vin": [ { "gen": { "height": 1068129 } } ], "vout": [ { "amount": 600000000, "target": { "key": "deb2c98c064b91d9b34c806ef9c577853651305f3cae55da6b0b65bce9ad7255" } } ], "extra": [ 1, 198, 122, 10, 151, 50, 120, 45, 42, 238, 97, 13, 206, 190, 42, 120, 53, 42, 166, 181, 189, 204, 67, 63, 163, 176, 186, 221, 24, 251, 218, 151, 200, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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