Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b40168d064de7beae01ec05d4be432b0dec58a5b0f392ab50d105a1e6d2307de

Tx prefix hash: 29ba0511b2bcc51f3a2016a9530ce17c18c67f8671605a83d8f8acc0fed6afb1
Tx public key: deb1fbae3b58c1b7ede14d58e2d5bc9db48423d5846bef84a4c92e702c12b247
Timestamp: 1728898014 Timestamp [UCT]: 2024-10-14 09:26:54 Age [y:d:h:m:s]: 00:160:00:01:27
Block: 1131330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114127 RingCT/type: yes/0
Extra: 01deb1fbae3b58c1b7ede14d58e2d5bc9db48423d5846bef84a4c92e702c12b24702110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07cd9be8e52a9a640de5d84d1b779596e1f296b348c13d5bd1dd83c669c0a5bd 0.600000000000 1614221 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": 1131340, "vin": [ { "gen": { "height": 1131330 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07cd9be8e52a9a640de5d84d1b779596e1f296b348c13d5bd1dd83c669c0a5bd" } } ], "extra": [ 1, 222, 177, 251, 174, 59, 88, 193, 183, 237, 225, 77, 88, 226, 213, 188, 157, 180, 132, 35, 213, 132, 107, 239, 132, 164, 201, 46, 112, 44, 18, 178, 71, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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