Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 812754967c5981071cad4d0ece577f4f4f23c8b70169d1985e470eb915aa2993

Tx prefix hash: 67e9e91bfe56e3ff6def0791d13d541aef8cbcd100ce466e8d00bdbe3f66683d
Tx public key: 99c58e5eaef5ec2d1a52d9601cbb2d4a490bd20d3be85105fa256b59a026b12d
Timestamp: 1725305983 Timestamp [UCT]: 2024-09-02 19:39:43 Age [y:d:h:m:s]: 00:258:06:07:49
Block: 1101543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184447 RingCT/type: yes/0
Extra: 0199c58e5eaef5ec2d1a52d9601cbb2d4a490bd20d3be85105fa256b59a026b12d021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96a20b8d65bf76e323f552e634765b21ca378c9064dbfdf047a7bbde6836629e 0.600000000000 1577634 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": 1101553, "vin": [ { "gen": { "height": 1101543 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96a20b8d65bf76e323f552e634765b21ca378c9064dbfdf047a7bbde6836629e" } } ], "extra": [ 1, 153, 197, 142, 94, 174, 245, 236, 45, 26, 82, 217, 96, 28, 187, 45, 74, 73, 11, 210, 13, 59, 232, 81, 5, 250, 37, 107, 89, 160, 38, 177, 45, 2, 17, 0, 0, 0, 1, 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