Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f8c7c764dbcffe179888629148e20a402df3641bfe6b4785222a6ad46582203

Tx prefix hash: 88d90cd3867fa8966594c4a8afcee277acf407d5cacf7b42a3fdee365c461a01
Tx public key: 65d8c4aeb1cfba5c88c120f55a45c29dfab276338c92a0d1365dc58e3e9ad94a
Timestamp: 1702582332 Timestamp [UCT]: 2023-12-14 19:32:12 Age [y:d:h:m:s]: 01:335:10:38:38
Block: 913147 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498609 RingCT/type: yes/0
Extra: 0165d8c4aeb1cfba5c88c120f55a45c29dfab276338c92a0d1365dc58e3e9ad94a021100000004faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c0eabd1357317b21e6298be2cc0602462f62d22e315d03ced3ac0f357d7398c 0.600000000000 1370393 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": 913157, "vin": [ { "gen": { "height": 913147 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c0eabd1357317b21e6298be2cc0602462f62d22e315d03ced3ac0f357d7398c" } } ], "extra": [ 1, 101, 216, 196, 174, 177, 207, 186, 92, 136, 193, 32, 245, 90, 69, 194, 157, 250, 178, 118, 51, 140, 146, 160, 209, 54, 93, 197, 142, 62, 154, 217, 74, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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