Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16ff4d2ad1712c3823e2e8e348ff0cfc2f68a4ddc2984e598789bd40dee3e3c2

Tx prefix hash: 783c5084a2d7e2f9446d9ced1f1a1cf6b8651dae9a6887a331c590ebc3938c28
Tx public key: 41b4a174d403a0e10748b4451c47ff3d6b06f40e2cd99ebc9b0375d01fcfa4c5
Timestamp: 1648879158 Timestamp [UCT]: 2022-04-02 05:59:18 Age [y:d:h:m:s]: 03:028:19:59:03
Block: 471428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 800988 RingCT/type: yes/0
Extra: 0141b4a174d403a0e10748b4451c47ff3d6b06f40e2cd99ebc9b0375d01fcfa4c5021100000003c9067537000000000000000000

1 output(s) for total of 16.825329744000 dcy

stealth address amount amount idx
00: b458d0cd07e2d48f1d3d57bc451f35e653349ff4d7e0cbda6db77ae8fab0cd63 16.825329744000 890772 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": 471438, "vin": [ { "gen": { "height": 471428 } } ], "vout": [ { "amount": 16825329744, "target": { "key": "b458d0cd07e2d48f1d3d57bc451f35e653349ff4d7e0cbda6db77ae8fab0cd63" } } ], "extra": [ 1, 65, 180, 161, 116, 212, 3, 160, 225, 7, 72, 180, 69, 28, 71, 255, 61, 107, 6, 244, 14, 44, 217, 158, 188, 155, 3, 117, 208, 31, 207, 164, 197, 2, 17, 0, 0, 0, 3, 201, 6, 117, 55, 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