Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed6c911b6fa09ff2e417294a20f37d2f0166a1610b9c720af3d29d2f4d173894

Tx prefix hash: e43fb475b18176d6961602b695681888f292bbf6ad6cbdf5f6cebacf53f86057
Tx public key: 932d5d81406859a1a9e69ba497aebd7dab80a9004f59aeb5b33fcbefc68e413c
Timestamp: 1687616264 Timestamp [UCT]: 2023-06-24 14:17:44 Age [y:d:h:m:s]: 01:203:19:29:17
Block: 789334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 407048 RingCT/type: yes/0
Extra: 01932d5d81406859a1a9e69ba497aebd7dab80a9004f59aeb5b33fcbefc68e413c02110000000533af99f4000000000000000000

1 output(s) for total of 1.488020572000 dcy

stealth address amount amount idx
00: 4c7fae344c0ac7da15387739b0fa3b2e0cd753bf2d51be640217cc55a0735d10 1.488020572000 1239547 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": 789344, "vin": [ { "gen": { "height": 789334 } } ], "vout": [ { "amount": 1488020572, "target": { "key": "4c7fae344c0ac7da15387739b0fa3b2e0cd753bf2d51be640217cc55a0735d10" } } ], "extra": [ 1, 147, 45, 93, 129, 64, 104, 89, 161, 169, 230, 155, 164, 151, 174, 189, 125, 171, 128, 169, 0, 79, 89, 174, 181, 179, 63, 203, 239, 198, 142, 65, 60, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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