Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9a4a7682eb641a1a12b15d5ea0ad243db284690b899da19df6d804e7f983e98

Tx prefix hash: 8819395380501409abe36fd2fdc9524a2ec4cb30e977174613240bb8fede7173
Tx public key: 2e6d7e761ef03b1ce26095d47f5d50c5782b310e03f6bf30a151664ea7b0df0a
Timestamp: 1702358249 Timestamp [UCT]: 2023-12-12 05:17:29 Age [y:d:h:m:s]: 01:176:23:00:55
Block: 911295 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 387651 RingCT/type: yes/0
Extra: 012e6d7e761ef03b1ce26095d47f5d50c5782b310e03f6bf30a151664ea7b0df0a021100000002faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85d2e45152586c3ebb4d1b6e6e61ad9e1541630481363db17327e633c574fd71 0.600000000000 1368476 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": 911305, "vin": [ { "gen": { "height": 911295 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85d2e45152586c3ebb4d1b6e6e61ad9e1541630481363db17327e633c574fd71" } } ], "extra": [ 1, 46, 109, 126, 118, 30, 240, 59, 28, 226, 96, 149, 212, 127, 93, 80, 197, 120, 43, 49, 14, 3, 246, 191, 48, 161, 81, 102, 78, 167, 176, 223, 10, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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