Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5c4efaa64e92b59a23cc7911c5244597d3001565a09eeaae8aa2d64078ec360

Tx prefix hash: d709650bcf439bce9851a7fa11707b3a2d22f67f746dc4435edd925e241e3ea1
Tx public key: ed51e024444174f8b8d1dc78f1c2b39f226dbb6bc27ea1dddc5075bcde2ea261
Timestamp: 1722669893 Timestamp [UCT]: 2024-08-03 07:24:53 Age [y:d:h:m:s]: 00:081:21:07:55
Block: 1079687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58625 RingCT/type: yes/0
Extra: 01ed51e024444174f8b8d1dc78f1c2b39f226dbb6bc27ea1dddc5075bcde2ea26102110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e207e08fb6cee08dc0e9881378370a56aa2f0bf40b4ad7c8e93fa306d74f6c38 0.600000000000 1552754 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": 1079697, "vin": [ { "gen": { "height": 1079687 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e207e08fb6cee08dc0e9881378370a56aa2f0bf40b4ad7c8e93fa306d74f6c38" } } ], "extra": [ 1, 237, 81, 224, 36, 68, 65, 116, 248, 184, 209, 220, 120, 241, 194, 179, 159, 34, 109, 187, 107, 194, 126, 161, 221, 220, 80, 117, 188, 222, 46, 162, 97, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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