Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 031f3d2fbe088f18cdf2b4b2cec6e0779c717ae3903715020c3cb273090b73e6

Tx prefix hash: 407ca1cd7af2a1b2e48052422993dbf5c0167e07c1776d30e2fc3425fbed4606
Tx public key: 54668da4fcb4c1131be32dd058249af14bb4d09e34d4760984ec8ff9cd98292a
Timestamp: 1704836417 Timestamp [UCT]: 2024-01-09 21:40:17 Age [y:d:h:m:s]: 01:081:13:27:25
Block: 931827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319397 RingCT/type: yes/0
Extra: 0154668da4fcb4c1131be32dd058249af14bb4d09e34d4760984ec8ff9cd98292a02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a114a603cd56d27036fd252e8a776f81eba4a3f2cbd0b8cdfb79b818e51e2e9 0.600000000000 1389731 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": 931837, "vin": [ { "gen": { "height": 931827 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a114a603cd56d27036fd252e8a776f81eba4a3f2cbd0b8cdfb79b818e51e2e9" } } ], "extra": [ 1, 84, 102, 141, 164, 252, 180, 193, 19, 27, 227, 45, 208, 88, 36, 154, 241, 75, 180, 208, 158, 52, 212, 118, 9, 132, 236, 143, 249, 205, 152, 41, 42, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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