Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3b2c5d82bfc6358bf4303be475224ac47bbd207369e0707f4fad55798c3055c

Tx prefix hash: ca58a1e6baed891a0ca3204bd86eb5fd94845adb1a1f2e1fc6f71f7d6b4f527e
Tx public key: b003270734bf75fdb473bf09470c937443cbfd95cecdb5af1dede51ee1368c66
Timestamp: 1722496365 Timestamp [UCT]: 2024-08-01 07:12:45 Age [y:d:h:m:s]: 01:102:07:50:39
Block: 1078255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331614 RingCT/type: yes/0
Extra: 01b003270734bf75fdb473bf09470c937443cbfd95cecdb5af1dede51ee1368c66021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61fcff6db68d6050e05ab5d1f8ad6c7db5248b925d726d6df6f11a24e45f3a30 0.600000000000 1550830 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": 1078265, "vin": [ { "gen": { "height": 1078255 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61fcff6db68d6050e05ab5d1f8ad6c7db5248b925d726d6df6f11a24e45f3a30" } } ], "extra": [ 1, 176, 3, 39, 7, 52, 191, 117, 253, 180, 115, 191, 9, 71, 12, 147, 116, 67, 203, 253, 149, 206, 205, 181, 175, 29, 237, 229, 30, 225, 54, 140, 102, 2, 17, 0, 0, 0, 3, 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