Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c360a175a7c21da935603050efd5a4c14af11ecc71ee95c99a75ce7bc2383668

Tx prefix hash: d1361b4105c7bcb3b98510f350f4a8677db496650bdccd5017c3dc0342a2b157
Tx public key: 553c7c9f42770dc44aa81004b86f3b222e378b7a26be49102949c5e8c66fb851
Timestamp: 1697086017 Timestamp [UCT]: 2023-10-12 04:46:57 Age [y:d:h:m:s]: 01:215:21:05:24
Block: 867796 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415339 RingCT/type: yes/0
Extra: 01553c7c9f42770dc44aa81004b86f3b222e378b7a26be49102949c5e8c66fb8510211000000134b8f5122000000000000000000

1 output(s) for total of 0.817770883000 dcy

stealth address amount amount idx
00: 7fd3526d56a1e8d2687b63f12f6f6823414b2191f2b7968babc992ad3f4d40dd 0.817770883000 1322514 of 0

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": 867806, "vin": [ { "gen": { "height": 867796 } } ], "vout": [ { "amount": 817770883, "target": { "key": "7fd3526d56a1e8d2687b63f12f6f6823414b2191f2b7968babc992ad3f4d40dd" } } ], "extra": [ 1, 85, 60, 124, 159, 66, 119, 13, 196, 74, 168, 16, 4, 184, 111, 59, 34, 46, 55, 139, 122, 38, 190, 73, 16, 41, 73, 197, 232, 198, 111, 184, 81, 2, 17, 0, 0, 0, 19, 75, 143, 81, 34, 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