Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7eaa7106cf4e4e21a45cd90eb78f3b5120cd4516e48a67f801268d43a73fdf9e

Tx prefix hash: 051e417e720e690dcbf0acff9e2aa152d2cccef5ee5028e131be50338451ff7c
Tx public key: 0c2b90409bfa6c2d1369ad71521a858ca1c61ff0451c72acf2277b926d7a8c3f
Timestamp: 1682536607 Timestamp [UCT]: 2023-04-26 19:16:47 Age [y:d:h:m:s]: 01:302:14:32:09
Block: 747211 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477491 RingCT/type: yes/0
Extra: 010c2b90409bfa6c2d1369ad71521a858ca1c61ff0451c72acf2277b926d7a8c3f021100000001b3164c24000000000000000000

1 output(s) for total of 2.052012406000 dcy

stealth address amount amount idx
00: b2747ce4a8a6bb685c1dfa9a70860a77f9be0e86b40ecbd7613db2ab73df63d4 2.052012406000 1194858 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": 747221, "vin": [ { "gen": { "height": 747211 } } ], "vout": [ { "amount": 2052012406, "target": { "key": "b2747ce4a8a6bb685c1dfa9a70860a77f9be0e86b40ecbd7613db2ab73df63d4" } } ], "extra": [ 1, 12, 43, 144, 64, 155, 250, 108, 45, 19, 105, 173, 113, 82, 26, 133, 140, 161, 198, 31, 240, 69, 28, 114, 172, 242, 39, 123, 146, 109, 122, 140, 63, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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