Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4b22f7df5bf3aa5392001dd0e6af3d69a1c64e340929b979d68122f5d44959d

Tx prefix hash: d6844edac06dc7f3aa74ff637a19ec34a53b4f4fb35de3b27126257316858c74
Tx public key: 7c746be8b10372fec795f803dda9edf089baf7c0317322ec84abd8a6f953a4de
Timestamp: 1717401280 Timestamp [UCT]: 2024-06-03 07:54:40 Age [y:d:h:m:s]: 00:284:07:58:52
Block: 1036019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203211 RingCT/type: yes/0
Extra: 017c746be8b10372fec795f803dda9edf089baf7c0317322ec84abd8a6f953a4de021100000001162613aa000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f65b173d6ae924ece0f7563ef5b445bc08b5e6eaf438abd17a95b24aaae106ab 0.600000000000 1504544 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": 1036029, "vin": [ { "gen": { "height": 1036019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f65b173d6ae924ece0f7563ef5b445bc08b5e6eaf438abd17a95b24aaae106ab" } } ], "extra": [ 1, 124, 116, 107, 232, 177, 3, 114, 254, 199, 149, 248, 3, 221, 169, 237, 240, 137, 186, 247, 192, 49, 115, 34, 236, 132, 171, 216, 166, 249, 83, 164, 222, 2, 17, 0, 0, 0, 1, 22, 38, 19, 170, 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