Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cf841fe5987df1b9111016ea0857906008a9396e2ed4763d734254fd5cb5846

Tx prefix hash: 4e795876035e1e10e25790a3f7cb5eb26b4193ab8e267f38c236e214f6e7224e
Tx public key: d4aa10b1fea3f11d7b700d2141b5ab0704706071d99bc6b2fa6a892121d47466
Timestamp: 1715943123 Timestamp [UCT]: 2024-05-17 10:52:03 Age [y:d:h:m:s]: 00:320:18:26:38
Block: 1023929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229257 RingCT/type: yes/0
Extra: 01d4aa10b1fea3f11d7b700d2141b5ab0704706071d99bc6b2fa6a892121d4746602110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dfe88c8e24ff78a66f44d573a017b323cb73ba1401c4ab5ca936740da476861a 0.600000000000 1489272 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": 1023939, "vin": [ { "gen": { "height": 1023929 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dfe88c8e24ff78a66f44d573a017b323cb73ba1401c4ab5ca936740da476861a" } } ], "extra": [ 1, 212, 170, 16, 177, 254, 163, 241, 29, 123, 112, 13, 33, 65, 181, 171, 7, 4, 112, 96, 113, 217, 155, 198, 178, 250, 106, 137, 33, 33, 212, 116, 102, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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