Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30e5fe0b2d9b6e4a20a35bd549deb86ac26c35f343f8d25b53a7875ea1ef76b6

Tx prefix hash: 32b62658e1ea8f1f91ede9267b3381313bc438d883468adef23e6ce1ca5cc29b
Tx public key: c98b359549823612f036e469a2efadc99bb0c4bcca86a8b396fc75cd85d69e2f
Timestamp: 1721772453 Timestamp [UCT]: 2024-07-23 22:07:33 Age [y:d:h:m:s]: 00:329:13:28:11
Block: 1072243 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235383 RingCT/type: yes/0
Extra: 01c98b359549823612f036e469a2efadc99bb0c4bcca86a8b396fc75cd85d69e2f021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d05e048811e79e9b6506462b08cac19b3d6e19fd75f4e4f1c649f86de6dc6186 0.600000000000 1544702 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": 1072253, "vin": [ { "gen": { "height": 1072243 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d05e048811e79e9b6506462b08cac19b3d6e19fd75f4e4f1c649f86de6dc6186" } } ], "extra": [ 1, 201, 139, 53, 149, 73, 130, 54, 18, 240, 54, 228, 105, 162, 239, 173, 201, 155, 176, 196, 188, 202, 134, 168, 179, 150, 252, 117, 205, 133, 214, 158, 47, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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