Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4c95839fadd8951c53f64dc7f0edf90dc5947fdb8497b253121d386765a5999

Tx prefix hash: eb49d547b4972d00a1c6194261430330c69e32d1c208e0ef12d8fede172801dc
Tx public key: d5a26a0b334bca6eb389d72b3fe275e21d1f4934c4b0d12ce8fb9a343b292435
Timestamp: 1624003785 Timestamp [UCT]: 2021-06-18 08:09:45 Age [y:d:h:m:s]: 03:320:02:15:49
Block: 279697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 995111 RingCT/type: yes/0
Extra: 01d5a26a0b334bca6eb389d72b3fe275e21d1f4934c4b0d12ce8fb9a343b29243502110000001f97247f25000000000000000000

1 output(s) for total of 72.652113222000 dcy

stealth address amount amount idx
00: 1fa7a5743cbe18937f5572c50c0b47be0301a0929f7b94843e394b207f8a1adb 72.652113222000 585738 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": 279707, "vin": [ { "gen": { "height": 279697 } } ], "vout": [ { "amount": 72652113222, "target": { "key": "1fa7a5743cbe18937f5572c50c0b47be0301a0929f7b94843e394b207f8a1adb" } } ], "extra": [ 1, 213, 162, 106, 11, 51, 75, 202, 110, 179, 137, 215, 43, 63, 226, 117, 226, 29, 31, 73, 52, 196, 176, 209, 44, 232, 251, 154, 52, 59, 41, 36, 53, 2, 17, 0, 0, 0, 31, 151, 36, 127, 37, 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