Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6ba1f38b32e063109c0411eef1845f40f5c9ae526fa3e85f17638e9942fcc04

Tx prefix hash: 02a3bbee6cd1f6e08c702d5e3d0af0beaeb4bdd7fad92066a57a5498ffea1c62
Tx public key: 9423e855f8a33ce3be852760a959d6aff9eda589a88adb578de2f39b3449430d
Timestamp: 1639039960 Timestamp [UCT]: 2021-12-09 08:52:40 Age [y:d:h:m:s]: 03:327:13:00:16
Block: 391650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1010554 RingCT/type: yes/0
Extra: 019423e855f8a33ce3be852760a959d6aff9eda589a88adb578de2f39b3449430d021100000001379224c2000000000000000000

1 output(s) for total of 30.924943551000 dcy

stealth address amount amount idx
00: e7786e08fe4beae5aad81e77356b73efaf93894ef3f07509d09aea4211e1d42c 30.924943551000 788113 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": 391660, "vin": [ { "gen": { "height": 391650 } } ], "vout": [ { "amount": 30924943551, "target": { "key": "e7786e08fe4beae5aad81e77356b73efaf93894ef3f07509d09aea4211e1d42c" } } ], "extra": [ 1, 148, 35, 232, 85, 248, 163, 60, 227, 190, 133, 39, 96, 169, 89, 214, 175, 249, 237, 165, 137, 168, 138, 219, 87, 141, 226, 243, 155, 52, 73, 67, 13, 2, 17, 0, 0, 0, 1, 55, 146, 36, 194, 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