Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f48e76711eb7d13dce79fce1026f8f9f59d7da839b7ea3a773d5ab2e2ec84de

Tx prefix hash: c2de183fd158d868b665a5c9cb7912a05ec9ca118f769fbc53d80687df4a1134
Tx public key: e79d8af41ce6bdc40bb8c6904ed4fc8da2902103a79f6bccd6922bdde841bbd3
Timestamp: 1723349276 Timestamp [UCT]: 2024-08-11 04:07:56 Age [y:d:h:m:s]: 01:167:23:39:11
Block: 1085323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378449 RingCT/type: yes/0
Extra: 01e79d8af41ce6bdc40bb8c6904ed4fc8da2902103a79f6bccd6922bdde841bbd302110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed83d8b6dc68e7ef7afbdb4a658e0aa02ba27b5cca206da159c0123c8242decd 0.600000000000 1559884 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": 1085333, "vin": [ { "gen": { "height": 1085323 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed83d8b6dc68e7ef7afbdb4a658e0aa02ba27b5cca206da159c0123c8242decd" } } ], "extra": [ 1, 231, 157, 138, 244, 28, 230, 189, 196, 11, 184, 198, 144, 78, 212, 252, 141, 162, 144, 33, 3, 167, 159, 107, 204, 214, 146, 43, 221, 232, 65, 187, 211, 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