Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b4dff542a8ffb8cd0d676aec57911409fbd8d449a79f9c361b3aa14e1307406

Tx prefix hash: 59c6105ba7b59816c041d54873f43a163a028ae646ef85fcf27918c8ec35ed3e
Tx public key: b5b590e9137b5cbc82a0f0aaa4d23b23dfdf1889e9b6fa4bc10b41c44025a761
Timestamp: 1723593581 Timestamp [UCT]: 2024-08-13 23:59:41 Age [y:d:h:m:s]: 00:313:05:27:37
Block: 1087347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223589 RingCT/type: yes/0
Extra: 01b5b590e9137b5cbc82a0f0aaa4d23b23dfdf1889e9b6fa4bc10b41c44025a761021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16f684c3083ba90a69945d5f8f230811977599299b9df0b626190923c981041d 0.600000000000 1561954 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": 1087357, "vin": [ { "gen": { "height": 1087347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16f684c3083ba90a69945d5f8f230811977599299b9df0b626190923c981041d" } } ], "extra": [ 1, 181, 181, 144, 233, 19, 123, 92, 188, 130, 160, 240, 170, 164, 210, 59, 35, 223, 223, 24, 137, 233, 182, 250, 75, 193, 11, 65, 196, 64, 37, 167, 97, 2, 17, 0, 0, 0, 8, 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