Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 228f0305f7b057122749fdbbaa77ca9c67c08d947748661c3b40ef08693b35b1

Tx prefix hash: 414e6ddf3093d345ececc1f782f7cfcae464c72bd6837950260548c67f49b787
Tx public key: 3cd7640637460f000722ac1b7359bf8df4d13df3e7d9f95eb6f3f4ee7cb9477d
Timestamp: 1638249982 Timestamp [UCT]: 2021-11-30 05:26:22 Age [y:d:h:m:s]: 03:147:09:05:46
Block: 385161 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 884050 RingCT/type: yes/0
Extra: 013cd7640637460f000722ac1b7359bf8df4d13df3e7d9f95eb6f3f4ee7cb9477d021100000006a272b9cb000000000000000000

1 output(s) for total of 32.493918902000 dcy

stealth address amount amount idx
00: fe6dbb66c6d8aab4bb42507ec315ee9462eb61015ea031a1c7fc32e74a07ddc3 32.493918902000 777290 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": 385171, "vin": [ { "gen": { "height": 385161 } } ], "vout": [ { "amount": 32493918902, "target": { "key": "fe6dbb66c6d8aab4bb42507ec315ee9462eb61015ea031a1c7fc32e74a07ddc3" } } ], "extra": [ 1, 60, 215, 100, 6, 55, 70, 15, 0, 7, 34, 172, 27, 115, 89, 191, 141, 244, 209, 61, 243, 231, 217, 249, 94, 182, 243, 244, 238, 124, 185, 71, 125, 2, 17, 0, 0, 0, 6, 162, 114, 185, 203, 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