Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b223882b2d9e3343c955f51964fdbed2217224fdef6d2209bef68c0469d9ce1b

Tx prefix hash: f36b0c43aae9cc1591293cfd451be594ea4aeb1aa7329b1a06a6f1d2c5302a44
Tx public key: 9927310616c9a03f071ca636b2e0fa5c9d8b9c7e5bf6b7b171ae2e4196567864
Timestamp: 1700928515 Timestamp [UCT]: 2023-11-25 16:08:35 Age [y:d:h:m:s]: 01:161:18:08:34
Block: 899441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376785 RingCT/type: yes/0
Extra: 019927310616c9a03f071ca636b2e0fa5c9d8b9c7e5bf6b7b171ae2e419656786402110000000475e3f0e9000000000000000000

1 output(s) for total of 0.642360127000 dcy

stealth address amount amount idx
00: 1d61e8f1d8a7bb6bfbb6a5969702448fbffe0ad8ec83f2c458cbc3055366a00a 0.642360127000 1355896 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": 899451, "vin": [ { "gen": { "height": 899441 } } ], "vout": [ { "amount": 642360127, "target": { "key": "1d61e8f1d8a7bb6bfbb6a5969702448fbffe0ad8ec83f2c458cbc3055366a00a" } } ], "extra": [ 1, 153, 39, 49, 6, 22, 201, 160, 63, 7, 28, 166, 54, 178, 224, 250, 92, 157, 139, 156, 126, 91, 246, 183, 177, 113, 174, 46, 65, 150, 86, 120, 100, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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