Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34bb158d59a5b5c38cb6f1a24f4c4aa7e62b6f465c1699c29a6968c357778fc4

Tx prefix hash: 485dbc1221518e709aec6ad11ed888811c49d8ffe599fe3f43cd2cba4339534e
Tx public key: 43810fd6ef5430abdb4bf173bc4fe1f4ccfd6184f0d17e12bcc002af4a213bb1
Timestamp: 1707884947 Timestamp [UCT]: 2024-02-14 04:29:07 Age [y:d:h:m:s]: 01:068:04:20:24
Block: 957110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309776 RingCT/type: yes/0
Extra: 0143810fd6ef5430abdb4bf173bc4fe1f4ccfd6184f0d17e12bcc002af4a213bb102110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 694a15e5bcfd5b3200f2e83f8927421c4e69cd8acd9486d613911f9696e79592 0.600000000000 1416426 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": 957120, "vin": [ { "gen": { "height": 957110 } } ], "vout": [ { "amount": 600000000, "target": { "key": "694a15e5bcfd5b3200f2e83f8927421c4e69cd8acd9486d613911f9696e79592" } } ], "extra": [ 1, 67, 129, 15, 214, 239, 84, 48, 171, 219, 75, 241, 115, 188, 79, 225, 244, 204, 253, 97, 132, 240, 209, 126, 18, 188, 192, 2, 175, 74, 33, 59, 177, 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