Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4643f20abd99510ef49e3c4ceaeba443118a848dc7ce48c856ad250c9cc8267

Tx prefix hash: e9bd1b2eadc12ab48e1d04ec78e93eebad7c83526db5ea1ff30df349cfb86114
Tx public key: b8a49b2793f0c8ca42ca0f075f4b554b913f47124dd5cb7d5ccba9957a45d771
Timestamp: 1725882783 Timestamp [UCT]: 2024-09-09 11:53:03 Age [y:d:h:m:s]: 00:121:17:42:51
Block: 1106334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87061 RingCT/type: yes/0
Extra: 01b8a49b2793f0c8ca42ca0f075f4b554b913f47124dd5cb7d5ccba9957a45d77102110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a22f5fe8b91bee135a5f0b519bd37fffe2f9a9452a3f7055a749ecdb7af12c68 0.600000000000 1583933 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": 1106344, "vin": [ { "gen": { "height": 1106334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a22f5fe8b91bee135a5f0b519bd37fffe2f9a9452a3f7055a749ecdb7af12c68" } } ], "extra": [ 1, 184, 164, 155, 39, 147, 240, 200, 202, 66, 202, 15, 7, 95, 75, 85, 75, 145, 63, 71, 18, 77, 213, 203, 125, 92, 203, 169, 149, 122, 69, 215, 113, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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