Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69f558ddea3e5b8b9b71cae1e33d85f5d712116362d1941069ab09c916d1d535

Tx prefix hash: 9cbf416a602efcd6dd49e7f2f68691196229de0b6c4ba95756f67fa1cefa73e4
Tx public key: c19c5ac6e6dc6976022280e928df6180f6820ff535d2a8751494d8f85417d2ba
Timestamp: 1712460641 Timestamp [UCT]: 2024-04-07 03:30:41 Age [y:d:h:m:s]: 01:214:18:47:57
Block: 995018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 412214 RingCT/type: yes/0
Extra: 01c19c5ac6e6dc6976022280e928df6180f6820ff535d2a8751494d8f85417d2ba02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dfac77fe44d2fd38c0026b00216488e0efd7ee5eda1c22b80ca17a1be497d5bc 0.600000000000 1455422 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": 995028, "vin": [ { "gen": { "height": 995018 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfac77fe44d2fd38c0026b00216488e0efd7ee5eda1c22b80ca17a1be497d5bc" } } ], "extra": [ 1, 193, 156, 90, 198, 230, 220, 105, 118, 2, 34, 128, 233, 40, 223, 97, 128, 246, 130, 15, 245, 53, 210, 168, 117, 20, 148, 216, 248, 84, 23, 210, 186, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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