Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca10bcbb810e6924be06cd221a507c3e0b94bc54a252b2734942dc28f1e2ac42

Tx prefix hash: 6df377c597ddf10a78ed823a220b0fb968b56ac32f0ce94a7879c68b3677c413
Tx public key: 1f600d0f2241c88dfa712d93850d10f09dbd31ee4d08eb6ec7b9c8e4db986518
Timestamp: 1716378270 Timestamp [UCT]: 2024-05-22 11:44:30 Age [y:d:h:m:s]: 00:246:20:55:43
Block: 1027540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176626 RingCT/type: yes/0
Extra: 011f600d0f2241c88dfa712d93850d10f09dbd31ee4d08eb6ec7b9c8e4db98651802110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ed80627de095bcd4123a6559bca3ab7292375773b038f8803e22a941152d494 0.600000000000 1495211 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": 1027550, "vin": [ { "gen": { "height": 1027540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ed80627de095bcd4123a6559bca3ab7292375773b038f8803e22a941152d494" } } ], "extra": [ 1, 31, 96, 13, 15, 34, 65, 200, 141, 250, 113, 45, 147, 133, 13, 16, 240, 157, 189, 49, 238, 77, 8, 235, 110, 199, 185, 200, 228, 219, 152, 101, 24, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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