Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7f155960df6e85a2b166c2baf00c753797368bcef5e9f2c534bf25d849fb280

Tx prefix hash: b6d911cc9662103035572246c25721b0b79c78bfe459c00e1296f2cfad53c3f2
Tx public key: d9c8e63abd5a609edcf91ccbfe87eff76824afaee2a48977b599daa79b061f4e
Timestamp: 1725291371 Timestamp [UCT]: 2024-09-02 15:36:11 Age [y:d:h:m:s]: 01:058:17:21:36
Block: 1101424 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300401 RingCT/type: yes/0
Extra: 01d9c8e63abd5a609edcf91ccbfe87eff76824afaee2a48977b599daa79b061f4e021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4330851f3b0e8fdbd0cd58503c64d940c39f68d71d9a6502ec1aa2bdc14d99ad 0.600000000000 1577469 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": 1101434, "vin": [ { "gen": { "height": 1101424 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4330851f3b0e8fdbd0cd58503c64d940c39f68d71d9a6502ec1aa2bdc14d99ad" } } ], "extra": [ 1, 217, 200, 230, 58, 189, 90, 96, 158, 220, 249, 28, 203, 254, 135, 239, 247, 104, 36, 175, 174, 226, 164, 137, 119, 181, 153, 218, 167, 155, 6, 31, 78, 2, 17, 0, 0, 0, 5, 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