Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bed7f6110e03b76d009694c4f23402bbe96db6cbbe4681ab73881991ccb95fe8

Tx prefix hash: 3efe5b99f75803f7b08040beeffb353b01c102036fd61c6bdfbab2f81ce1cd73
Tx public key: 0667a8299d7416f0e86869e31f62270c84e6acd5e69bd9a41d14b2f1d5c0c740
Timestamp: 1734713342 Timestamp [UCT]: 2024-12-20 16:49:02 Age [y:d:h:m:s]: 00:081:22:03:46
Block: 1179446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58315 RingCT/type: yes/0
Extra: 010667a8299d7416f0e86869e31f62270c84e6acd5e69bd9a41d14b2f1d5c0c7400211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a81144f4e6a75ca900f2ee03780161eb7cc8573e9b1948e8fbe33349b06f062a 0.600000000000 1665841 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": 1179456, "vin": [ { "gen": { "height": 1179446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a81144f4e6a75ca900f2ee03780161eb7cc8573e9b1948e8fbe33349b06f062a" } } ], "extra": [ 1, 6, 103, 168, 41, 157, 116, 22, 240, 232, 104, 105, 227, 31, 98, 39, 12, 132, 230, 172, 213, 230, 155, 217, 164, 29, 20, 178, 241, 213, 192, 199, 64, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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