Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82479e54471b186cb86975456f9b7358bc7159a91ccc0d5d30549857f1560498

Tx prefix hash: bbad08f130c179889d60e6e98f52eb5e1cc781192c0ed698b30722d45b56f62e
Tx public key: a19521147143f25aea34b1ae2b9c8f7a0ccb5a72a65e66ad3e1902c3d4778e15
Timestamp: 1703670887 Timestamp [UCT]: 2023-12-27 09:54:47 Age [y:d:h:m:s]: 01:315:10:13:15
Block: 922178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484256 RingCT/type: yes/0
Extra: 01a19521147143f25aea34b1ae2b9c8f7a0ccb5a72a65e66ad3e1902c3d4778e15021100000002ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0c800cf4eef26242174f8eef083196e84aca77c939d3a5d8cd7e76a8338aa69 0.600000000000 1379872 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": 922188, "vin": [ { "gen": { "height": 922178 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0c800cf4eef26242174f8eef083196e84aca77c939d3a5d8cd7e76a8338aa69" } } ], "extra": [ 1, 161, 149, 33, 20, 113, 67, 242, 90, 234, 52, 177, 174, 43, 156, 143, 122, 12, 203, 90, 114, 166, 94, 102, 173, 62, 25, 2, 195, 212, 119, 142, 21, 2, 17, 0, 0, 0, 2, 173, 86, 148, 172, 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