Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc2aa7f6b9b159af052624ec0e91447c57896dbb7671e44f44700d1640ee3c32

Tx prefix hash: 863d524df6bbf38141bf20cb7711962e357d516641ba3086b7a8e1cb1c7680ca
Tx public key: 4edff8713abaafed3cdf42367d3eeb2f79647ab0a2f9872c55ad8df43cffef04
Timestamp: 1730808196 Timestamp [UCT]: 2024-11-05 12:03:16 Age [y:d:h:m:s]: 00:154:00:05:23
Block: 1147068 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109894 RingCT/type: yes/0
Extra: 014edff8713abaafed3cdf42367d3eeb2f79647ab0a2f9872c55ad8df43cffef04021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e5253311b8e28e566c43e32d8347fc392e83dd67ddd39e93a4185cc6b4b6bf8b 0.600000000000 1631761 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": 1147078, "vin": [ { "gen": { "height": 1147068 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e5253311b8e28e566c43e32d8347fc392e83dd67ddd39e93a4185cc6b4b6bf8b" } } ], "extra": [ 1, 78, 223, 248, 113, 58, 186, 175, 237, 60, 223, 66, 54, 125, 62, 235, 47, 121, 100, 122, 176, 162, 249, 135, 44, 85, 173, 141, 244, 60, 255, 239, 4, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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