Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69716e6c848444deee0d3eead6c7efbe07c985d5423b9d95955d557252ebf98c

Tx prefix hash: b9348f958578f4a979ca5c70752e6a294484c067af09d0f2e00ca8fee6e177b8
Tx public key: ae674bffdf2533a1c550720fa3a155cf1cc7eb0ae0020d023f81c4924756bf70
Timestamp: 1682170555 Timestamp [UCT]: 2023-04-22 13:35:55 Age [y:d:h:m:s]: 01:308:16:42:24
Block: 744174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 481851 RingCT/type: yes/0
Extra: 01ae674bffdf2533a1c550720fa3a155cf1cc7eb0ae0020d023f81c4924756bf70021100000002b3164c24000000000000000000

1 output(s) for total of 2.100113798000 dcy

stealth address amount amount idx
00: 98f30a28467c28d4f09794a8c6e4cf06e212f9213adb04b0e2dd0874446c35ab 2.100113798000 1191439 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": 744184, "vin": [ { "gen": { "height": 744174 } } ], "vout": [ { "amount": 2100113798, "target": { "key": "98f30a28467c28d4f09794a8c6e4cf06e212f9213adb04b0e2dd0874446c35ab" } } ], "extra": [ 1, 174, 103, 75, 255, 223, 37, 51, 161, 197, 80, 114, 15, 163, 161, 85, 207, 28, 199, 235, 10, 224, 2, 13, 2, 63, 129, 196, 146, 71, 86, 191, 112, 2, 17, 0, 0, 0, 2, 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