Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 241e818f64795a8f68bba3cefb08dce8eab78368f202c9f3c9cfc275dcf2fec6

Tx prefix hash: df2ed572d1f1b2f0576b922be6088084482b1aaf16012d71d4c1087c8945ae4a
Tx public key: c68edae4ac71d8170c9f796a8ef0429d73434157be0e9a0faffdab72e2a90cfa
Timestamp: 1736370637 Timestamp [UCT]: 2025-01-08 21:10:37 Age [y:d:h:m:s]: 00:079:01:16:36
Block: 1193134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56279 RingCT/type: yes/0
Extra: 01c68edae4ac71d8170c9f796a8ef0429d73434157be0e9a0faffdab72e2a90cfa021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6527c3947354f27c45a9b9fde96a21bcdb82d7dd50d52eb461af98f8a059f9e 0.600000000000 1679693 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": 1193144, "vin": [ { "gen": { "height": 1193134 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6527c3947354f27c45a9b9fde96a21bcdb82d7dd50d52eb461af98f8a059f9e" } } ], "extra": [ 1, 198, 142, 218, 228, 172, 113, 216, 23, 12, 159, 121, 106, 142, 240, 66, 157, 115, 67, 65, 87, 190, 14, 154, 15, 175, 253, 171, 114, 226, 169, 12, 250, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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