Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7c356c33a1281f4abfdec1a245ba49c55aa81b817425afa90c970df21734a79

Tx prefix hash: a4a788a508b62e8a753e7242b9312536c62c7cd97a14ddc19f9136fe67d514ba
Tx public key: be5305b5e6bf73c6376958556dc11567d9c8c5b67bdc6d35325c456dcaea80a9
Timestamp: 1712576084 Timestamp [UCT]: 2024-04-08 11:34:44 Age [y:d:h:m:s]: 01:000:20:49:37
Block: 995985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261594 RingCT/type: yes/0
Extra: 01be5305b5e6bf73c6376958556dc11567d9c8c5b67bdc6d35325c456dcaea80a90211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07591b378dfdb018c03cbd04433a87f9b3e5e9a9742fc7263a92789463d8500c 0.600000000000 1456401 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": 995995, "vin": [ { "gen": { "height": 995985 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07591b378dfdb018c03cbd04433a87f9b3e5e9a9742fc7263a92789463d8500c" } } ], "extra": [ 1, 190, 83, 5, 181, 230, 191, 115, 198, 55, 105, 88, 85, 109, 193, 21, 103, 217, 200, 197, 182, 123, 220, 109, 53, 50, 92, 69, 109, 202, 234, 128, 169, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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