Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5d3248f7f76ce170d623146c3a89d786bb88e190c8b26f906dee012a69a8210

Tx prefix hash: a96fd9eaab78a443223a89550bf5240c45c4dd9c699f36cba77afcc5d053650c
Tx public key: e57610e7e2646840a63b0164e869139bb0ed56f37bf4a2e09f8eabce6af0dd13
Timestamp: 1708943293 Timestamp [UCT]: 2024-02-26 10:28:13 Age [y:d:h:m:s]: 01:043:16:57:32
Block: 965898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292251 RingCT/type: yes/0
Extra: 01e57610e7e2646840a63b0164e869139bb0ed56f37bf4a2e09f8eabce6af0dd13021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4748ef96cc6da25e807d09dd492d55b7ac3de0e0dce7b69da9959415fb25c03e 0.600000000000 1425653 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": 965908, "vin": [ { "gen": { "height": 965898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4748ef96cc6da25e807d09dd492d55b7ac3de0e0dce7b69da9959415fb25c03e" } } ], "extra": [ 1, 229, 118, 16, 231, 226, 100, 104, 64, 166, 59, 1, 100, 232, 105, 19, 155, 176, 237, 86, 243, 123, 244, 162, 224, 159, 142, 171, 206, 106, 240, 221, 19, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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