Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68af69ca85e1c2a106de5cfe1301714b8adddaceb81b2b765a14af413f0e7953

Tx prefix hash: 3f78e3bf63dfcc0a758e0257fc2f7ccfa8f9f505ada6b72c774700c0f57bd660
Tx public key: e95c3f3970a2c7cea68d9299b42c0677425772f7f896c677489d4cd7bd0e2fb7
Timestamp: 1719532337 Timestamp [UCT]: 2024-06-27 23:52:17 Age [y:d:h:m:s]: 00:327:01:13:31
Block: 1053677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233738 RingCT/type: yes/0
Extra: 01e95c3f3970a2c7cea68d9299b42c0677425772f7f896c677489d4cd7bd0e2fb70211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0098084353d540658442fb35ace2dc88e6c40447d949d525181deaa1aaa63f5 0.600000000000 1524024 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": 1053687, "vin": [ { "gen": { "height": 1053677 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0098084353d540658442fb35ace2dc88e6c40447d949d525181deaa1aaa63f5" } } ], "extra": [ 1, 233, 92, 63, 57, 112, 162, 199, 206, 166, 141, 146, 153, 180, 44, 6, 119, 66, 87, 114, 247, 248, 150, 198, 119, 72, 157, 76, 215, 189, 14, 47, 183, 2, 17, 0, 0, 0, 2, 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