Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88f9f13481fabcb22f0f96025daa6b7b5c5637176241ce9fb6a01e9556db01da

Tx prefix hash: 8b3ced09fce5b441ed9c9aafa469754936978393ab8818e344ca896916baedf8
Tx public key: 7c428616dc24f2f52ce61cb1852cd6f3633d1b770a1ff5a4d7c0e6d9633f857b
Timestamp: 1711889598 Timestamp [UCT]: 2024-03-31 12:53:18 Age [y:d:h:m:s]: 01:041:06:21:01
Block: 990337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290454 RingCT/type: yes/0
Extra: 017c428616dc24f2f52ce61cb1852cd6f3633d1b770a1ff5a4d7c0e6d9633f857b02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3a678312559e26f41df5a72991d7e8ad8575413176a2b8adfe82368ddf53870 0.600000000000 1450659 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": 990347, "vin": [ { "gen": { "height": 990337 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3a678312559e26f41df5a72991d7e8ad8575413176a2b8adfe82368ddf53870" } } ], "extra": [ 1, 124, 66, 134, 22, 220, 36, 242, 245, 44, 230, 28, 177, 133, 44, 214, 243, 99, 61, 27, 119, 10, 31, 245, 164, 215, 192, 230, 217, 99, 63, 133, 123, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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