Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55940c00a311b7229c67635e05bbdad2ddaa2cef291fcc1acdc45b7a4c41cf34

Tx prefix hash: d5792c8be96f0875daf461b0bd0537e7205b72de482de61b666d26ab3d41b39e
Tx public key: f7e9babc1489a7c7d50ac1b0cbd394a879e8ccf929b053f547f5732287bbd255
Timestamp: 1679857168 Timestamp [UCT]: 2023-03-26 18:59:28 Age [y:d:h:m:s]: 02:015:17:38:34
Block: 725658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 532764 RingCT/type: yes/0
Extra: 01f7e9babc1489a7c7d50ac1b0cbd394a879e8ccf929b053f547f5732287bbd255021100000001b3164c24000000000000000000

1 output(s) for total of 3.345405062000 dcy

stealth address amount amount idx
00: a5f823ca3de7fb4a163f39faaa695ff1481baf813cc5c020a7f25e48ae159e24 3.345405062000 1170801 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": 725668, "vin": [ { "gen": { "height": 725658 } } ], "vout": [ { "amount": 3345405062, "target": { "key": "a5f823ca3de7fb4a163f39faaa695ff1481baf813cc5c020a7f25e48ae159e24" } } ], "extra": [ 1, 247, 233, 186, 188, 20, 137, 167, 199, 213, 10, 193, 176, 203, 211, 148, 168, 121, 232, 204, 249, 41, 176, 83, 245, 71, 245, 115, 34, 135, 187, 210, 85, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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