Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5dbb821fa93a396f822f92710bbddc364689336893f94f4a5f10b49386c4ba6e

Tx prefix hash: c93ebd8e6f1b8d9ddda511ffd9e5c2069ea9aec4c593f710ee07b04e6562dfc3
Tx public key: 8661341a3cb0f9796d1fa61284b98e59e7337347f3b9bbe7b018867d1a5b6b93
Timestamp: 1727089837 Timestamp [UCT]: 2024-09-23 11:10:37 Age [y:d:h:m:s]: 00:198:00:34:53
Block: 1116335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141349 RingCT/type: yes/0
Extra: 018661341a3cb0f9796d1fa61284b98e59e7337347f3b9bbe7b018867d1a5b6b93021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5963cf3b84687a196d854e924a51f4bee3c48a455ddc181dd685a3d68327d5b7 0.600000000000 1596782 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": 1116345, "vin": [ { "gen": { "height": 1116335 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5963cf3b84687a196d854e924a51f4bee3c48a455ddc181dd685a3d68327d5b7" } } ], "extra": [ 1, 134, 97, 52, 26, 60, 176, 249, 121, 109, 31, 166, 18, 132, 185, 142, 89, 231, 51, 115, 71, 243, 185, 187, 231, 176, 24, 134, 125, 26, 91, 107, 147, 2, 17, 0, 0, 0, 8, 233, 20, 221, 21, 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