Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 638e1af8d72ef198a889c34cdb0f9466826de67728fb0133126eb8d4eb05e240

Tx prefix hash: 35ff742af09e9e16c8c6b26a8504da68fa45f7d4ace849aef793e62924c6d903
Tx public key: fc9891fa6842d4971894e5dc80c2339580d83b9e65fe1da162b51f2aead61a43
Timestamp: 1648655319 Timestamp [UCT]: 2022-03-30 15:48:39 Age [y:d:h:m:s]: 02:286:20:26:13
Block: 469667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 724632 RingCT/type: yes/0
Extra: 01fc9891fa6842d4971894e5dc80c2339580d83b9e65fe1da162b51f2aead61a430211000000094a0f5013000000000000000000

1 output(s) for total of 17.052910429000 dcy

stealth address amount amount idx
00: db83010c1a9f747afa68eb2fe7b8e7a32de0ffa3cb4d2f342c5193e10b49ef00 17.052910429000 888651 of 0

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": 469677, "vin": [ { "gen": { "height": 469667 } } ], "vout": [ { "amount": 17052910429, "target": { "key": "db83010c1a9f747afa68eb2fe7b8e7a32de0ffa3cb4d2f342c5193e10b49ef00" } } ], "extra": [ 1, 252, 152, 145, 250, 104, 66, 212, 151, 24, 148, 229, 220, 128, 194, 51, 149, 128, 216, 59, 158, 101, 254, 29, 161, 98, 181, 31, 42, 234, 214, 26, 67, 2, 17, 0, 0, 0, 9, 74, 15, 80, 19, 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