Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb7ac9afe966fbca667103b3574b0f054d932eddf4b6ce1dfb9c3e72194108ed

Tx prefix hash: 3e60f3c5fa6080cd76780a5b5e3f3491da41b934c12db018f2862a112df00c4a
Tx public key: 1a796605e5bca4a5658e4497eca03be818498654f4c896eda469f9aaf4be9e4f
Timestamp: 1716136252 Timestamp [UCT]: 2024-05-19 16:30:52 Age [y:d:h:m:s]: 00:325:08:40:22
Block: 1025521 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232557 RingCT/type: yes/0
Extra: 011a796605e5bca4a5658e4497eca03be818498654f4c896eda469f9aaf4be9e4f02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 060b3460f940704b7043f7e88cd477abfb0db013e9c988237e2a019545811b47 0.600000000000 1492090 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": 1025531, "vin": [ { "gen": { "height": 1025521 } } ], "vout": [ { "amount": 600000000, "target": { "key": "060b3460f940704b7043f7e88cd477abfb0db013e9c988237e2a019545811b47" } } ], "extra": [ 1, 26, 121, 102, 5, 229, 188, 164, 165, 101, 142, 68, 151, 236, 160, 59, 232, 24, 73, 134, 84, 244, 200, 150, 237, 164, 105, 249, 170, 244, 190, 158, 79, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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