Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04a97b190a908393fb35de39034004a0d2416efbbdaf14154de1ca4d16d9cfe3

Tx prefix hash: bde01b16a20a24b2d7a93b3a2c089dd7c743eeb9c8a3e9ba23d63d586dd77733
Tx public key: 9682374d74a9148288850a75c2b33a4179f63ae5556d55d7fde7065899909dc0
Timestamp: 1719685590 Timestamp [UCT]: 2024-06-29 18:26:30 Age [y:d:h:m:s]: 00:195:08:54:33
Block: 1054950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139795 RingCT/type: yes/0
Extra: 019682374d74a9148288850a75c2b33a4179f63ae5556d55d7fde7065899909dc00211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70a9793948c0a8fd24fe80a57c36244a5edc32db67f4e5d95a684bb7d7ff0d20 0.600000000000 1525341 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": 1054960, "vin": [ { "gen": { "height": 1054950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70a9793948c0a8fd24fe80a57c36244a5edc32db67f4e5d95a684bb7d7ff0d20" } } ], "extra": [ 1, 150, 130, 55, 77, 116, 169, 20, 130, 136, 133, 10, 117, 194, 179, 58, 65, 121, 246, 58, 229, 85, 109, 85, 215, 253, 231, 6, 88, 153, 144, 157, 192, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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