Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f96c352dfee1eb0ac424e96f6a0f52558ad4f88bebc4df2ad4d2e668a6c3b972

Tx prefix hash: 737f82cbdd5a64e95db0905a5935934dc2d11849b9a754baecd4719638f7593d
Tx public key: e40034bbcdce5db4998956b33d461b02c502816694e665ffd5d51fd27c6acc3c
Timestamp: 1710585729 Timestamp [UCT]: 2024-03-16 10:42:09 Age [y:d:h:m:s]: 01:009:19:23:12
Block: 979526 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267956 RingCT/type: yes/0
Extra: 01e40034bbcdce5db4998956b33d461b02c502816694e665ffd5d51fd27c6acc3c02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33ed6dad124bfb9792a8af4d58b40ff1eba309eb22629fbf876dc4ead95cab6f 0.600000000000 1439561 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": 979536, "vin": [ { "gen": { "height": 979526 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33ed6dad124bfb9792a8af4d58b40ff1eba309eb22629fbf876dc4ead95cab6f" } } ], "extra": [ 1, 228, 0, 52, 187, 205, 206, 93, 180, 153, 137, 86, 179, 61, 70, 27, 2, 197, 2, 129, 102, 148, 230, 101, 255, 213, 213, 31, 210, 124, 106, 204, 60, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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