Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab1375967b67e6c5310d1df3537ce8b02126b8aba4eb898d57763b7df52c7822

Tx prefix hash: 8cd8f76324a952551d6fa340cc4ac08dda5bc2f9fe7c3b3db96abe3ee38915a3
Tx public key: dc8ebd868de61e12c8d557b5f71b333a55e5bb47b34a4c0f812646c65af12228
Timestamp: 1721304961 Timestamp [UCT]: 2024-07-18 12:16:01 Age [y:d:h:m:s]: 00:254:18:18:57
Block: 1068393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181971 RingCT/type: yes/0
Extra: 01dc8ebd868de61e12c8d557b5f71b333a55e5bb47b34a4c0f812646c65af1222802110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf609514721b9c02874478c2df6c1689c5e54a5421e6f06dc8e920398ff70b0c 0.600000000000 1539470 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": 1068403, "vin": [ { "gen": { "height": 1068393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf609514721b9c02874478c2df6c1689c5e54a5421e6f06dc8e920398ff70b0c" } } ], "extra": [ 1, 220, 142, 189, 134, 141, 230, 30, 18, 200, 213, 87, 181, 247, 27, 51, 58, 85, 229, 187, 71, 179, 74, 76, 15, 129, 38, 70, 198, 90, 241, 34, 40, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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