Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b9e3c0be7e1f03b639f31fc62094c2e4b7bd7a34a77f3e4a13f8e704546ea3d

Tx prefix hash: 72c01d382481b1a218e1f1f917b02080d0bed474276b9f61b60af672ca6c33b3
Tx public key: 63ca64b41f2a2e7bcbb49afd015e7f23b4e81a84358cc61da787f8cc14d2dc6b
Timestamp: 1721691670 Timestamp [UCT]: 2024-07-22 23:41:10 Age [y:d:h:m:s]: 00:233:20:22:56
Block: 1071567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167067 RingCT/type: yes/0
Extra: 0163ca64b41f2a2e7bcbb49afd015e7f23b4e81a84358cc61da787f8cc14d2dc6b02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63ef308b1d20f5fb37e9ee1738b40b058251cf28078073d92460b50f9b28ab40 0.600000000000 1543844 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": 1071577, "vin": [ { "gen": { "height": 1071567 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63ef308b1d20f5fb37e9ee1738b40b058251cf28078073d92460b50f9b28ab40" } } ], "extra": [ 1, 99, 202, 100, 180, 31, 42, 46, 123, 203, 180, 154, 253, 1, 94, 127, 35, 180, 232, 26, 132, 53, 140, 198, 29, 167, 135, 248, 204, 20, 210, 220, 107, 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