Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22e95ec147a24f01f186f86d11684163227510d09834404ae0ce2e5d7bea12c4

Tx prefix hash: 986180d4c6f83404e8d3591445d86518b4b4f0b765c4aff5cf86ba6fa2752f57
Tx public key: 2567c61015a1d946b10e772a85da8d20a0dfe0bc246bccf0775fb20d3638ded8
Timestamp: 1730858446 Timestamp [UCT]: 2024-11-06 02:00:46 Age [y:d:h:m:s]: 00:001:10:55:11
Block: 1147485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1053 RingCT/type: yes/0
Extra: 012567c61015a1d946b10e772a85da8d20a0dfe0bc246bccf0775fb20d3638ded8021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0af4c1ccf58184cdca29733f0bfb41e6562142b5e05300aa6c8d2f02d100d02 0.600000000000 1632182 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": 1147495, "vin": [ { "gen": { "height": 1147485 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0af4c1ccf58184cdca29733f0bfb41e6562142b5e05300aa6c8d2f02d100d02" } } ], "extra": [ 1, 37, 103, 198, 16, 21, 161, 217, 70, 177, 14, 119, 42, 133, 218, 141, 32, 160, 223, 224, 188, 36, 107, 204, 240, 119, 95, 178, 13, 54, 56, 222, 216, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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