Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61a37720ca38aeddc5fc8f1621596a159f9033e89a74a6a58e804b12745e1d96

Tx prefix hash: 36288b2bc25be03033f54216a423168c71b6eeb748ec4af8476a556db6a3245b
Tx public key: 4c7f107b0229e1c660aa70fa0d39c4be5db7e2d410c1ef61ea53d2880a8a81f8
Timestamp: 1728901765 Timestamp [UCT]: 2024-10-14 10:29:25 Age [y:d:h:m:s]: 00:172:04:03:37
Block: 1131360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122830 RingCT/type: yes/0
Extra: 014c7f107b0229e1c660aa70fa0d39c4be5db7e2d410c1ef61ea53d2880a8a81f8021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68a784678874d16a5916fb27bdf408ce142caf98a21893ba118767abd3156e12 0.600000000000 1614257 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": 1131370, "vin": [ { "gen": { "height": 1131360 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68a784678874d16a5916fb27bdf408ce142caf98a21893ba118767abd3156e12" } } ], "extra": [ 1, 76, 127, 16, 123, 2, 41, 225, 198, 96, 170, 112, 250, 13, 57, 196, 190, 93, 183, 226, 212, 16, 193, 239, 97, 234, 83, 210, 136, 10, 138, 129, 248, 2, 17, 0, 0, 0, 4, 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