Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e543a78d7a4b9f34c92e3e66fcb5c2bda283cc58a9b34d835a0cc708cb00bae0

Tx prefix hash: 6d948b5898183cb74375ca5bf652647e6835c98b3e605c362f77a58773db1fee
Tx public key: f0de4c7854891c65915d47f8e552cec0c6a0efa3e770a20797a93f6097afc475
Timestamp: 1706348597 Timestamp [UCT]: 2024-01-27 09:43:17 Age [y:d:h:m:s]: 01:313:14:50:32
Block: 944357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 482974 RingCT/type: yes/0
Extra: 01f0de4c7854891c65915d47f8e552cec0c6a0efa3e770a20797a93f6097afc47502110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13a7ba1b7b680c96265043855f55fdec47c67efbb46efce58f27f6cdd5882476 0.600000000000 1402593 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": 944367, "vin": [ { "gen": { "height": 944357 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13a7ba1b7b680c96265043855f55fdec47c67efbb46efce58f27f6cdd5882476" } } ], "extra": [ 1, 240, 222, 76, 120, 84, 137, 28, 101, 145, 93, 71, 248, 229, 82, 206, 192, 198, 160, 239, 163, 231, 112, 162, 7, 151, 169, 63, 96, 151, 175, 196, 117, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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