Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e17fb7947f8cd9743b7f454c7fb98df3be5246ec4e4c74820255f673ade92c37

Tx prefix hash: 7bde60f81d09a809f67e2d08f9f30f0df9981561d229c064844f1cc0a2cc7c03
Tx public key: ec7415643ee9ece35da78e64acd1fd48482dc8d13cd6ed00db60e57bb8d8b6ca
Timestamp: 1711414105 Timestamp [UCT]: 2024-03-26 00:48:25 Age [y:d:h:m:s]: 01:020:23:11:26
Block: 986399 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275933 RingCT/type: yes/0
Extra: 01ec7415643ee9ece35da78e64acd1fd48482dc8d13cd6ed00db60e57bb8d8b6ca02110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f5b3e31ce00bf34ff8b1d8abdd25f24def6971b115e62f326a02c9b7152cd76e 0.600000000000 1446628 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": 986409, "vin": [ { "gen": { "height": 986399 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f5b3e31ce00bf34ff8b1d8abdd25f24def6971b115e62f326a02c9b7152cd76e" } } ], "extra": [ 1, 236, 116, 21, 100, 62, 233, 236, 227, 93, 167, 142, 100, 172, 209, 253, 72, 72, 45, 200, 209, 60, 214, 237, 0, 219, 96, 229, 123, 184, 216, 182, 202, 2, 17, 0, 0, 0, 8, 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